OpenEdge Application Server:<br />Administration Creating an OpenEdge service instance

If necessary, start the SonicMQ Domain Manager container and then start the SonicMQ Management Console.

On the Management Console menu bar, select Tools and then Sonic ESB Explorer.

In the left pane of the Sonic ESB Explorer, click the plus symbol (+) next to Services to expand the display of the folder contents.

In the expanded list of contents of the Services folder, select OpenEdge Services.

In the right pane, click New. The custom form for specifying OpenEdge service attributes goes into editable mode, as shown:

In the Service Namespace area of the right pane:

The first six fields (those above the horizontal separator line) are for specifying standard attributes common to all Sonic ESB services (see Step 6 through Step 9 below).

The remaining fields (those below the horizontal separator line) are for specifying attributes specific to OpenEdge services (see Step 10 through Step 16 below).

Of the properties common to all Sonic ESB services, only the service name (comparable to the friendly name for a WSA-based Web service) is required. Enter a unique name in the Service Name field.

Optionally, you can specify an entry endpoint, an exit endpoint, a fault endpoint, and a rejected message endpoint for the service. Service endpoints function as logical connections between services and are used as routing mechanisms. An endpoint can be a SonicMQ queue or topic, a service, or a process. See the Sonic ESB Developer’s Guide for more information about endpoints.

You can specify an existing endpoint or create a new one for use as any of the four endpoint values. Click the ellipsis (...) button to the right of an endpoint field (for example, Entry Endpoint) to display the Select Endpoint window, as shown:

Do one of the following:

Select an existing endpoint from the list.

Click New; select Endpoint, Service, or Process; then select the desired option from the submenu to display the Configure Endpoint window. Enter the appropriate values and click OK to return to the Select Endpoint window.

At the Select Entry Endpoint window, click OK.

Repeat Step 7 to specify the remaining endpoints.

Optionally specify a WSDL file to be associated with the OpenEdge service. This is typically the WSDL file generated by means of the OpenEdge resource editor. For more information on generating a WSDL file, see the "Generating a WSDL file from the OpenEdge Resource Editor" section.

To specify a WSDL file, it must already be stored in the sonicfs directory. Click the ellipsis (...) button and the Choose WSDL File Resource window appears:

Browse to select the WSDL file. Choose Open.

The WSDL is now associated with your service.

Of the attributes specific to OpenEdge services, only the OpenEdge Service Definition File field requires that you supply a value. You must specify a valid WSM or WSD file.

Click the ellipsis (...) button to the right of this field. The OpenEdgeMapping File window appears:

If the WSM or WSD file you want has already been loaded into the Sonic ESB Directory Service, select it from the list in the OpenEdgeMapping File window and click OK. Then skip to Step 15.

If the WSM or WSD file has not yet been loaded, click Create New Resource to display the Create Resource window, as shown:

In the Create Resource window, click Load from File to display a file browser. Navigate to the directory containing the appropriate WSM or WSD file, select the file, and click Open to return to the Create Resource window.

Click OK in the Create Resource window to return to the OpenEdgeMapping File window.

Click OK in the OpenEdgeMapping File window.

The value in the SOAP Fault Processing field determines the action taken when the AppServer returns a SOAP fault message. SOAP faults result from conditions such as the server not running or a message being improperly formatted; they are not caused by application errors.

Choose one of three values from the drop-down menu that appears when you click the down arrow at the right of the field:

None — No fault processing occurs. As is always the case with any response from the AppServer, the SOAP fault message is simply sent to the service’s exit endpoint, if any, or to the next step specified in the process itinerary.

Message — The message that was being processed when the SOAP fault was generated is sent to the service’s fault endpoint or to the fault endpoint specified in the process definition. The message can be processed after the fault is corrected.

Fault — The SOAP fault message is sent to the service’s fault endpoint or to the fault endpoint specified in the process definition (perhaps triggering an alert to a person who can take the appropriate corrective action). The message that was being processed when the SOAP fault was generated is lost.

Note: If the SOAP Fault Processing field is set to Message or Fault, the service definition or the process definition must specify a fault endpoint. Otherwise, a SOAP fault causes an exception.

Enter values in the remaining fields only if you want to override the default values in the WSM or WSD file specified in the OpenEdge Service Definition File field. If values are entered for them, these properties override the defaults as follows:

AppServer Protocol — Overrides the appServiceProtocol default property.

AppServer Host — Overrides the appServiceHost default property.

AppServer Port — Overrides the appServicePort default property.

OpenEdge AppService Name — Overrides the appServiceName default property.

Disable SSL Hostname Verification — Overrides the noHostVerify default property.

Disable SSL Session reuse — Overrides the noSessionReuse default property.

For an explanation of these and other service properties, see Appendix A "Reference to Progress 4GL Web Service Properties."

Click Apply at the bottom of the right pane of the Sonic ESB Explorer to create the service instance.

Generating a WSDL file from the OpenEdge Resource Editor

You have the option of associating a WSDL file with your service. By generating the correct WSDL file and associating it with your service, you can use the Sonic Web Services Call Composer to generate calls to your service from a workflow.

Open the Sonic ESB Explorer.

In the left pane of the Sonic ESB Explorer window, click the Resources node.

From the Resources node, select the WSM file of your service. The Edit OpenEdgeService Definition appears, as shown:

Click the Generate WSDL button to bring up the Generate WSDL dialog, as shown:

Specify a Web Service URL that points directly to the service using a sonic: URL address. A sonic: URL address consists of three slash-delimited parts, as shown in the following table:


Address part	Example	Description
sonic:///	sonic:///	Represents the Sonic protocol with no host or port.
node/	local/	Represents the defined entry endpoint for the service or process, or local for `localhost`.
ServiceName	QuoteService	Represents the name of the service.

For more information, see Sonic ESB Developer’s Guide provided by Sonic Software Corporation.

In the File Name field, specify a File Name for the WSDL file by either typing the absolute or relative pathname or click Browse, navigate to the directory where you want to create the file, enter a filename, and click Open.

Click OK to generate the WSDL file and save it locally.